IBX-10688: SiteAccess-aware Raptor connector configuration documented in Dev-doc by julitafalcondusza · Pull Request #3101 · ibexa/documentation-developer

julitafalcondusza · 2026-03-20T13:12:30Z

Question	Answer
JIRA Ticket	IBX-10688 ibexa/connector-raptor#2
Versions	5.0
Editions	Headless+

SiteAccess-aware Raptor connector configuration documented in Dev-doc

Checklist

Text renders correctly
Text has been checked with vale
Description metadata is up to date
Redirects cover removed/moved pages
Code samples are working
PHP code samples have been fixed with PHP CS fixer
Added link to this PR in relevant JIRA ticket or code PR

github-actions · 2026-03-20T13:12:50Z

Preview of modified files

Preview of modified Markdown:

alongosz

It looks good, but would be nice to see this in preview build which is currently failing

adriendupuis

I was confused in the first place by the fact that we already have Raptor features, so, why needing a new connector?… Before understanding the Recommandation scope of this new thing. This should be clarified.

It should also be clear that it's an LTS Update.

docs/cdp/raptor_integration/raptor_connector.md

docs/recommendations/raptor_integration/raptor_connector.md

docs/cdp/raptor_integration/raptor_connector.md

docs/recommendations/raptor_integration/raptor_connector.md

docs/recommendations/raptor_integration/connector_configuration.md

docs/cdp/raptor_integration/connector_configuration.md

docs/recommendations/raptor_integration/connector_configuration.md

docs/cdp/raptor_integration/connector_configuration.md

theme/partials/nav-item.html

docs/recommendations/raptor_integration/connector_configuration.md

docs/cdp/raptor_integration/raptor_connector.md

docs/recommendations/raptor_integration/raptor_connector.md

docs/recommendations/raptor_integration/connector_configuration.md

docs/cdp/raptor_integration/raptor_connector.md

docs/recommendations/raptor_integration/connector_configuration.md

sonarqubecloud · 2026-04-03T09:07:26Z

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

github-actions · 2026-04-03T09:07:31Z

code_samples/ change report

Before (on target branch) After (in current PR)


code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml


code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml

docs/recommendations/raptor_integration/connector_configuration.md@18:``` yaml
docs/recommendations/raptor_integration/connector_configuration.md@19:[[= include_file('code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml', 1, 14) =]]
docs/recommendations/raptor_integration/connector_configuration.md@20:```

001⫶    system:
002⫶        <scope>:
003⫶            connector_raptor:
004⫶                enabled:              true
005⫶                customer_id:          ~ # Required
006⫶                tracking_type:        client # One of: "client" or "server"
007⫶
008⫶                # Raptor Recommendations API key
009⫶                recommendations_api_key: ~ # Required
010⫶
011⫶                # Raptor Recommendations API URL, optional, set by default
012⫶                recommendations_api_url: '%ibexa.connector.raptor.recommendations.api_url%'
013⫶ibexa_connector_raptor:

docs/recommendations/raptor_integration/connector_configuration.md@66:``` yaml hl_lines="14-17"
docs/recommendations/raptor_integration/connector_configuration.md@67:[[= include_file('code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml') =]]
docs/recommendations/raptor_integration/connector_configuration.md@68:```

001⫶ibexa:
002⫶    system:
003⫶        <scope>:
004⫶            connector_raptor:
005⫶                enabled:              true
006⫶                customer_id:          ~ # Required
007⫶                tracking_type:        client # One of: "client" or "server"
008⫶
009⫶                # Raptor Recommendations API key
010⫶                recommendations_api_key: ~ # Required
011⫶
012⫶                # Raptor Recommendations API URL, optional, set by default
013⫶                recommendations_api_url: '%ibexa.connector.raptor.recommendations.api_url%'
014❇️ibexa_connector_raptor:
015❇️    # When enabled, tracking exceptions are thrown instead of being silently handled
016❇️    strict_exceptions: true

Download colorized diff

dabrt · 2026-04-03T14:39:06Z

docs/recommendations/raptor_integration/connector_configuration.md

+[[= include_file('code_samples/recommendations/config/packages/ibexa_connector_raptor.yaml', 1, 14) =]]
+```
+
+- `enabled` - enables or disables the Connector for a given scope, default value: `true`. If set to `false`, no tracking or recommendation requests are executed.


Suggested change

- `enabled` - enables or disables the Connector for a given scope, default value: `true`. If set to `false`, no tracking or recommendation requests are executed.

- `enabled` - enables or disables the connector for a given scope, default value: `true`. If set to `false`, no tracking or recommendation requests are executed.

dabrt · 2026-04-03T14:40:53Z

docs/recommendations/raptor_integration/connector_configuration.md

+description: Step-by-step configuration procedure of the Raptor connector.
+---
+
+# Installation


Suggested change

# Installation

# Configure Raptor connector

dabrt · 2026-04-03T14:42:32Z

docs/recommendations/raptor_integration/connector_configuration.md

+
+# Installation
+
+First, install the Raptor connector.


Suggested change

First, install the Raptor connector.

Before you can proceed to configuring the integration with Raptor, install the connector.

dabrt · 2026-04-03T14:43:11Z

docs/recommendations/raptor_integration/connector_configuration.md

@@ -0,0 +1,68 @@
+---
+description: Step-by-step configuration procedure of the Raptor connector.
+---


Suggested change

---

month_change: true

---

dabrt · 2026-04-03T14:44:38Z

docs/recommendations/raptor_integration/connector_configuration.md

+
+# SiteAccess-aware configuration
+
+To configure Raptor connector, use the `ibexa.system.<scope>.connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file:


Suggested change

To configure Raptor connector, use the `ibexa.system.<scope>.connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file:

To configure the Raptor connector, use the `ibexa.system.<scope>.connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file:

dabrt · 2026-04-03T15:07:19Z

docs/recommendations/raptor_integration/raptor_connector.md

+
+The [Raptor](https://www.raptorservices.com/) connector provides a seamless integration between [[= product_name =]] and Raptor Recommendation Engine.
+
+Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.


Suggested change

Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.

Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps increase conversion rates, drive sales, and improve user engagement.

dabrt · 2026-04-03T15:07:47Z

docs/recommendations/raptor_integration/raptor_connector.md

+
+Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.
+
+By combining content management capabilities with advanced recommendation features, the Connector allows teams to build and manage personalized experiences directly within a single platform.


Suggested change

By combining content management capabilities with advanced recommendation features, the Connector allows teams to build and manage personalized experiences directly within a single platform.

By combining content management capabilities with advanced recommendation features, the connector allows teams to build and manage personalized experiences directly within a single platform.

dabrt · 2026-04-03T15:08:05Z

docs/recommendations/raptor_integration/raptor_connector.md

+
+By combining content management capabilities with advanced recommendation features, the Connector allows teams to build and manage personalized experiences directly within a single platform.
+
+This connector ensures a smooth and unified integration layer, enabling:


Suggested change

This connector ensures a smooth and unified integration layer, enabling:

The connector ensures a smooth and unified integration layer, enabling:

dabrt · 2026-04-03T15:09:26Z

docs/recommendations/raptor_integration/raptor_connector.md

+
+This approach reduces integration complexity while providing a scalable foundation for personalization use cases across multiple sites and markets.
+
+To configure the Raptor integration. follow a step-by-step procedure that allows you to activate the Raptor connector.


Suggested change

To configure the Raptor integration. follow a step-by-step procedure that allows you to activate the Raptor connector.

To configure the integration with Raptor, follow a step-by-step procedure that allows you to activate the Raptor connector.

dabrt · 2026-04-03T15:12:01Z

docs/recommendations/raptor_integration/raptor_connector.md

+description: Step-by-step activation procedure of setting up the Raptor connector.
+page_type: landing_page
+---


Suggested change

description: Step-by-step activation procedure of setting up the Raptor connector.

page_type: landing_page

---

description: Deliver personalized experiences across digital channels with the Raptor connector.

page_type: landing_page

month_change: true

---

raptor connector configuration

92ae029

julitafalcondusza added 3 commits March 20, 2026 14:14

mkdocs updated

b138e44

links updated/added

e769a20

fix in the list

d16400a

alongosz approved these changes Mar 30, 2026

View reviewed changes

julitafalcondusza added 2 commits March 30, 2026 14:28

link fixed

72be3b9

img added

23f96e6

julitafalcondusza marked this pull request as ready for review March 30, 2026 12:43

julitafalcondusza added the Needs DEV review label Mar 30, 2026

tbialcz approved these changes Mar 31, 2026

View reviewed changes

julitafalcondusza added Needs DOC review and removed Needs DEV review labels Mar 31, 2026

adriendupuis added the Wait with merge PRs that shouldn't be merged instantly label Apr 1, 2026

adriendupuis mentioned this pull request Apr 1, 2026

Release notes #3076

Draft

7 tasks

cards added

03934df

adriendupuis requested changes Apr 2, 2026

View reviewed changes

mnocon reviewed Apr 2, 2026

View reviewed changes

docs/cdp/raptor_integration/raptor_connector.md Outdated Show resolved Hide resolved

docs/recommendations/raptor_integration/connector_configuration.md Outdated Show resolved Hide resolved

adriendupuis mentioned this pull request Apr 2, 2026

IBX-11150: Recommendation blocks described in Dev-doc #3103

Open

7 tasks

julitafalcondusza added 5 commits April 3, 2026 09:05

fixes

65bd319

nav-item file fixed

dadaacf

fixes

36e0183

fix

2027610

fixes - second batch

ea6a782

julitafalcondusza requested review from adriendupuis and mnocon April 3, 2026 11:34

dabrt requested changes Apr 3, 2026

View reviewed changes

	- `enabled` - enables or disables the Connector for a given scope, default value: `true`. If set to `false`, no tracking or recommendation requests are executed.
	- `enabled` - enables or disables the connector for a given scope, default value: `true`. If set to `false`, no tracking or recommendation requests are executed.

	First, install the Raptor connector.
	Before you can proceed to configuring the integration with Raptor, install the connector.


		# SiteAccess-aware configuration

		To configure Raptor connector, use the `ibexa.system.<scope>.connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file:

	To configure Raptor connector, use the `ibexa.system.<scope>.connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file:
	To configure the Raptor connector, use the `ibexa.system.<scope>.connector_raptor` configuration key in the `config/packages/ibexa_connector_raptor.yaml` file:


		The [Raptor](https://www.raptorservices.com/) connector provides a seamless integration between [[= product_name =]] and Raptor Recommendation Engine.

		Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.


		Its primary goal is to enable editors and managers to deliver personalized experiences across digital channels, which helps to increase conversion rates, drive sales, and improve user engagement.

		By combining content management capabilities with advanced recommendation features, the Connector allows teams to build and manage personalized experiences directly within a single platform.


		By combining content management capabilities with advanced recommendation features, the Connector allows teams to build and manage personalized experiences directly within a single platform.

		This connector ensures a smooth and unified integration layer, enabling:

	This connector ensures a smooth and unified integration layer, enabling:
	The connector ensures a smooth and unified integration layer, enabling:


		This approach reduces integration complexity while providing a scalable foundation for personalization use cases across multiple sites and markets.

		To configure the Raptor integration. follow a step-by-step procedure that allows you to activate the Raptor connector.

	To configure the Raptor integration. follow a step-by-step procedure that allows you to activate the Raptor connector.
	To configure the integration with Raptor, follow a step-by-step procedure that allows you to activate the Raptor connector.

Conversation

julitafalcondusza commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Checklist

Uh oh!

github-actions bot commented Mar 20, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Preview of modified files

Uh oh!

alongosz left a comment

Choose a reason for hiding this comment

Uh oh!

adriendupuis left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

sonarqubecloud bot commented Apr 3, 2026

Quality Gate passed

Uh oh!

github-actions bot commented Apr 3, 2026

code_samples/ change report

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

6 participants

julitafalcondusza commented Mar 20, 2026 •

edited

Loading

github-actions bot commented Mar 20, 2026 •

edited

Loading